Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614142a74e6d955677f534d1ad8d18ae8a433cc2c2f11ea2bec3a5f7d039a68a

Tx prefix hash: 3a2f65b8e23bdb26e6c5cb37da29a8957e4e394a60e60c50fab478773c117827
Tx public key: afd2dcc5d0f0778fbce06310237f83e1f8fb70944d726f88269c3d40e20695a6
Timestamp: 1745520285 Timestamp [UCT]: 2025-04-24 18:44:45 Age [y:d:h:m:s]: 00:012:03:14:55
Block: 1268620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8672 RingCT/type: yes/0
Extra: 01afd2dcc5d0f0778fbce06310237f83e1f8fb70944d726f88269c3d40e20695a6021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa390fa993e1bc8b9b35351ae21bba7cef83cb1a7f0cc20300c0091fc63febf1 0.600000000000 1755851 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": 1268630, "vin": [ { "gen": { "height": 1268620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa390fa993e1bc8b9b35351ae21bba7cef83cb1a7f0cc20300c0091fc63febf1" } } ], "extra": [ 1, 175, 210, 220, 197, 208, 240, 119, 143, 188, 224, 99, 16, 35, 127, 131, 225, 248, 251, 112, 148, 77, 114, 111, 136, 38, 156, 61, 64, 226, 6, 149, 166, 2, 17, 0, 0, 0, 1, 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