Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94d2f32d6bb8e72c6f16fa8444551529fd5a90e6aaa4cdb31a13a0f2ab892b41

Tx prefix hash: 728a5165264c40e54be1ef405672ddd8070f086734cd2624d7291f1eb9a0786d
Tx public key: 0b575e51b68ed86b9aea626a853530a4f53671514c2459aaabedfbeab6cb8590
Timestamp: 1760856217 Timestamp [UCT]: 2025-10-19 06:43:37 Age [y:d:h:m:s]: 00:039:23:55:45
Block: 1393175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28616 RingCT/type: yes/0
Extra: 010b575e51b68ed86b9aea626a853530a4f53671514c2459aaabedfbeab6cb8590021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d95abde648e989f227a99294544024b0baceffa32ed1b9bbc1c5d7ffd6c52a6 0.600000000000 1881434 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": 1393185, "vin": [ { "gen": { "height": 1393175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d95abde648e989f227a99294544024b0baceffa32ed1b9bbc1c5d7ffd6c52a6" } } ], "extra": [ 1, 11, 87, 94, 81, 182, 142, 216, 107, 154, 234, 98, 106, 133, 53, 48, 164, 245, 54, 113, 81, 76, 36, 89, 170, 171, 237, 251, 234, 182, 203, 133, 144, 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