Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 886f98b2c695d0f6ae4ac59f7b7f20da92721cf00dc6bd0434043e04a0893f19

Tx prefix hash: cc7b93136f2486444acdea5a74da46c4c95e51c319ae1d5c98a868ea04752114
Tx public key: f78df1595ac1c79ce830266e07dfb40c4a65b02d1258ddccd0cae34c8f8e0924
Timestamp: 1716368670 Timestamp [UCT]: 2024-05-22 09:04:30 Age [y:d:h:m:s]: 00:185:19:21:20
Block: 1027459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132986 RingCT/type: yes/0
Extra: 01f78df1595ac1c79ce830266e07dfb40c4a65b02d1258ddccd0cae34c8f8e09240211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 333ecf7bf5b09b6398bf6b4ea7644d8d0847fb22079bcf0c9293a0a2f9941d1e 0.600000000000 1495086 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": 1027469, "vin": [ { "gen": { "height": 1027459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "333ecf7bf5b09b6398bf6b4ea7644d8d0847fb22079bcf0c9293a0a2f9941d1e" } } ], "extra": [ 1, 247, 141, 241, 89, 90, 193, 199, 156, 232, 48, 38, 110, 7, 223, 180, 12, 74, 101, 176, 45, 18, 88, 221, 204, 208, 202, 227, 76, 143, 142, 9, 36, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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