Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574b33e4df6799b140fe1f706f8a38728991b60de73ffebf78d69bbe3d07fe99

Tx prefix hash: 03afd016f55a62e76751e96e0b63098f994aea3e8a8d00208c90c2ba0eb0732d
Tx public key: ed59fe7ac7b28949030844a96d70cb6ca1e4226c8b6a37316207a388b6cb4315
Timestamp: 1727610357 Timestamp [UCT]: 2024-09-29 11:45:57 Age [y:d:h:m:s]: 01:040:02:15:28
Block: 1120654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287037 RingCT/type: yes/0
Extra: 01ed59fe7ac7b28949030844a96d70cb6ca1e4226c8b6a37316207a388b6cb431502110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 443df9d99a4c520c709161edaea8273bb9dcc70d1bafda4411d4117ad6fcc9a3 0.600000000000 1602647 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": 1120664, "vin": [ { "gen": { "height": 1120654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "443df9d99a4c520c709161edaea8273bb9dcc70d1bafda4411d4117ad6fcc9a3" } } ], "extra": [ 1, 237, 89, 254, 122, 199, 178, 137, 73, 3, 8, 68, 169, 109, 112, 203, 108, 161, 228, 34, 108, 139, 106, 55, 49, 98, 7, 163, 136, 182, 203, 67, 21, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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