Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5056631ce82ef37005a5da4d776743485fc121a14e49b5ef5082dbb95eb2b4

Tx prefix hash: 1909beae1e2ba318238490767825a7a8045e34b8d35e6c2b91cb4b42b5f2a456
Tx public key: 5f85a68a83cb6e3d9090b9d164c97ba617dd5d95917d2d4edd89332616871be8
Timestamp: 1750135470 Timestamp [UCT]: 2025-06-17 04:44:30 Age [y:d:h:m:s]: 00:200:17:01:14
Block: 1306710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141321 RingCT/type: yes/0
Extra: 015f85a68a83cb6e3d9090b9d164c97ba617dd5d95917d2d4edd89332616871be8021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c5df6de7e68612db5db7fc1cb190e319518a0543cba96102331d00d83675973 0.600000000000 1794317 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": 1306720, "vin": [ { "gen": { "height": 1306710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c5df6de7e68612db5db7fc1cb190e319518a0543cba96102331d00d83675973" } } ], "extra": [ 1, 95, 133, 166, 138, 131, 203, 110, 61, 144, 144, 185, 209, 100, 201, 123, 166, 23, 221, 93, 149, 145, 125, 45, 78, 221, 137, 51, 38, 22, 135, 27, 232, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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