Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b55aafcb73d5d0f3084ddc0fe94b5ea6eadccce378aa1d068a89697bd9472ba8

Tx prefix hash: 8f1d973ebaa048a637ea9f95136410836d73221f83939b13ca7df34efb89afb3
Tx public key: fe8e96547d7add51d3c85081376b6386b09fe9673ecfe24602ab53e0e54bcea6
Timestamp: 1744299080 Timestamp [UCT]: 2025-04-10 15:31:20 Age [y:d:h:m:s]: 00:221:11:30:25
Block: 1258506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156022 RingCT/type: yes/0
Extra: 01fe8e96547d7add51d3c85081376b6386b09fe9673ecfe24602ab53e0e54bcea60211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd6ca994d8589b810ed34f6f9a85840204dbf02f8bdbe99b81fa1cfd8e779893 0.600000000000 1745639 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": 1258516, "vin": [ { "gen": { "height": 1258506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd6ca994d8589b810ed34f6f9a85840204dbf02f8bdbe99b81fa1cfd8e779893" } } ], "extra": [ 1, 254, 142, 150, 84, 125, 122, 221, 81, 211, 200, 80, 129, 55, 107, 99, 134, 176, 159, 233, 103, 62, 207, 226, 70, 2, 171, 83, 224, 229, 75, 206, 166, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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