Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cacc8f8e5859da15a766c096c05de48007f862c462fe6db3cbb1a6e6dc1e97a1

Tx prefix hash: 0572a300fdcf1bcef90438295f7ac8696a77d626d26f6fc2d0b908ea17add157
Tx public key: 618c1a3df60cfdd6046e5860a7476d23a62ef8df6bd3f812d7e7337d89711da7
Timestamp: 1721341326 Timestamp [UCT]: 2024-07-18 22:22:06 Age [y:d:h:m:s]: 00:260:10:20:16
Block: 1068686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186052 RingCT/type: yes/0
Extra: 01618c1a3df60cfdd6046e5860a7476d23a62ef8df6bd3f812d7e7337d89711da7021100000005e914dd15000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: ffbb5663f84e41c2eee1a94a3a8b667d0dafb076f004550fd42a4403520f85e1 0.615600000000 1539811 of 0

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": 1068696, "vin": [ { "gen": { "height": 1068686 } } ], "vout": [ { "amount": 615600000, "target": { "key": "ffbb5663f84e41c2eee1a94a3a8b667d0dafb076f004550fd42a4403520f85e1" } } ], "extra": [ 1, 97, 140, 26, 61, 246, 12, 253, 214, 4, 110, 88, 96, 167, 71, 109, 35, 166, 46, 248, 223, 107, 211, 248, 18, 215, 231, 51, 125, 137, 113, 29, 167, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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