Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 621407e75c608eb5b02557def82649aae18a7461ade4e83afafa28f8db694fb9

Tx prefix hash: 8eccc69a320496a045580a6b83116335af5867c95ea7a040a6fb44ac00b68e17
Tx public key: 47dd08d1991a9b8313df8f4188e98039f6e284a07329cb20fe1fb8adbdf8eff1
Timestamp: 1735609752 Timestamp [UCT]: 2024-12-31 01:49:12 Age [y:d:h:m:s]: 00:310:19:42:41
Block: 1186833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219640 RingCT/type: yes/0
Extra: 0147dd08d1991a9b8313df8f4188e98039f6e284a07329cb20fe1fb8adbdf8eff1021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7e30f3898b8b88c5b61d3ee0d5dca50054da67ba84f69f499d88e4f946d5703 0.600000000000 1673318 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": 1186843, "vin": [ { "gen": { "height": 1186833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7e30f3898b8b88c5b61d3ee0d5dca50054da67ba84f69f499d88e4f946d5703" } } ], "extra": [ 1, 71, 221, 8, 209, 153, 26, 155, 131, 19, 223, 143, 65, 136, 233, 128, 57, 246, 226, 132, 160, 115, 41, 203, 32, 254, 31, 184, 173, 189, 248, 239, 241, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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