Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4d1055e06cd9044ddb3ceef68fc3ab07283e43b691f5d79492891e75165a6d12

Tx prefix hash: 5fd0a6f96cf86d520e90d77a4cfbe1f8d05e33179eb549983c92ebc966a34bae
Tx public key: f5fafe8b9209ed02903e111b84c37db9dd7c6e2f76f7f111beb04589b8114a92
Timestamp: 1738026534 Timestamp [UCT]: 2025-01-28 01:08:54 Age [y:d:h:m:s]: 00:143:13:33:25
Block: 1206601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102504 RingCT/type: yes/0
Extra: 01f5fafe8b9209ed02903e111b84c37db9dd7c6e2f76f7f111beb04589b8114a92021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ac27d90adeb8ea25d774c580d035c3291f81c651a8f811a28486d9814e3db7 0.600000000000 1693312 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1206611, "vin": [ { "gen": { "height": 1206601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ac27d90adeb8ea25d774c580d035c3291f81c651a8f811a28486d9814e3db7" } } ], "extra": [ 1, 245, 250, 254, 139, 146, 9, 237, 2, 144, 62, 17, 27, 132, 195, 125, 185, 221, 124, 110, 47, 118, 247, 241, 17, 190, 176, 69, 137, 184, 17, 74, 146, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8