Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec904021bf359714f6c0188cc26cda3307bcc79d801ce8a4898058d845b8e062

Tx prefix hash: 81b26e6045a664dfe353e1ff5ef9c8e68275ed05156ee1e537e20bb981a9a3ee
Tx public key: 9ec2516f9a0d79e788f70a8e24dfcda5fda1d32e3ca9286d418f5507bb90389c
Timestamp: 1721522124 Timestamp [UCT]: 2024-07-21 00:35:24 Age [y:d:h:m:s]: 00:298:03:33:00
Block: 1070169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213032 RingCT/type: yes/0
Extra: 019ec2516f9a0d79e788f70a8e24dfcda5fda1d32e3ca9286d418f5507bb90389c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 642d40530b439b9ef706e26fbf6bb3db0d6f4c744ec30fa0e3cc3c606990f98a 0.600000000000 1541894 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": 1070179, "vin": [ { "gen": { "height": 1070169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "642d40530b439b9ef706e26fbf6bb3db0d6f4c744ec30fa0e3cc3c606990f98a" } } ], "extra": [ 1, 158, 194, 81, 111, 154, 13, 121, 231, 136, 247, 10, 142, 36, 223, 205, 165, 253, 161, 211, 46, 60, 169, 40, 109, 65, 143, 85, 7, 187, 144, 56, 156, 2, 17, 0, 0, 0, 6, 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