Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6087fc247a54e64af35fce2264c93641cef97d2d68e7b43f815a3c7576e892ee

Tx prefix hash: 920a54d5b3b86f9580525fc63382a76494c21e6be6ecc4593e5cb21ffcbd06f1
Tx public key: 5162c136844e84a1cb027e22933b0ba9ccb4a2f9fa49aafbae7ca0d28bfa2c50
Timestamp: 1736110738 Timestamp [UCT]: 2025-01-05 20:58:58 Age [y:d:h:m:s]: 00:300:03:01:39
Block: 1191000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211986 RingCT/type: yes/0
Extra: 015162c136844e84a1cb027e22933b0ba9ccb4a2f9fa49aafbae7ca0d28bfa2c5002110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3906c969238d8711f4f16748d2a182f0aeae76d64b56707e613a43fdc5fa0dda 0.600000000000 1677523 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": 1191010, "vin": [ { "gen": { "height": 1191000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3906c969238d8711f4f16748d2a182f0aeae76d64b56707e613a43fdc5fa0dda" } } ], "extra": [ 1, 81, 98, 193, 54, 132, 78, 132, 161, 203, 2, 126, 34, 147, 59, 11, 169, 204, 180, 162, 249, 250, 73, 170, 251, 174, 124, 160, 210, 139, 250, 44, 80, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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