Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f9d1713a3ac605b7b02499229dca4ec549fda9df76fb2298e41eef98d5f32c9

Tx prefix hash: c6fdbc50592a8d099fa4667340ae4865e6cf872c0c693bd75a930f25e353dbb1
Tx public key: 477d222f15e452e9f4ec07525aa3ad0a946e5480fdacab0bf400e607abcb8501
Timestamp: 1744142060 Timestamp [UCT]: 2025-04-08 19:54:20 Age [y:d:h:m:s]: 00:035:23:47:34
Block: 1257200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25760 RingCT/type: yes/0
Extra: 01477d222f15e452e9f4ec07525aa3ad0a946e5480fdacab0bf400e607abcb85010211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3209ec2567aa3f9e23d72f0c590f591118b512580c61fdde5f4e683125087e1 0.600000000000 1744319 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": 1257210, "vin": [ { "gen": { "height": 1257200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3209ec2567aa3f9e23d72f0c590f591118b512580c61fdde5f4e683125087e1" } } ], "extra": [ 1, 71, 125, 34, 47, 21, 228, 82, 233, 244, 236, 7, 82, 90, 163, 173, 10, 148, 110, 84, 128, 253, 172, 171, 11, 244, 0, 230, 7, 171, 203, 133, 1, 2, 17, 0, 0, 0, 1, 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