Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93f9ca0d55823b0bff12d417cf2647b5c3307f5592c292ae32855259f4baef05

Tx prefix hash: 62006ee4c33fcf0c723d230fd8be8850d3d49c5765e7c25c6b314b973e86afad
Tx public key: d1753ee8ab04ba2bd28e3f143a7d807f0fa8430adfdf3bf06e94aecdafb083f5
Timestamp: 1704286375 Timestamp [UCT]: 2024-01-03 12:52:55 Age [y:d:h:m:s]: 01:091:22:59:42
Block: 927281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326819 RingCT/type: yes/0
Extra: 01d1753ee8ab04ba2bd28e3f143a7d807f0fa8430adfdf3bf06e94aecdafb083f50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 403f00a4af8ce70d5ac9bd52e3d9486e763b07f2e0d68a025e0dd2c779a18b47 0.600000000000 1385113 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": 927291, "vin": [ { "gen": { "height": 927281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "403f00a4af8ce70d5ac9bd52e3d9486e763b07f2e0d68a025e0dd2c779a18b47" } } ], "extra": [ 1, 209, 117, 62, 232, 171, 4, 186, 43, 210, 142, 63, 20, 58, 125, 128, 127, 15, 168, 67, 10, 223, 223, 59, 240, 110, 148, 174, 205, 175, 176, 131, 245, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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