Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638bfc2dd5b95f216bc0a9826ec234a740127b64be0e3171b51b0cbf8e857dc3

Tx prefix hash: 34ca83d44f5f2e198d22eb7aa01b45d905af8c1f531d8fed5608620fbafbe9f0
Tx public key: d09b364841e8663703466f9cf17a95a4152f02f1f7b980e96e18bf2c77d7c707
Timestamp: 1730920915 Timestamp [UCT]: 2024-11-06 19:21:55 Age [y:d:h:m:s]: 00:177:18:10:30
Block: 1148007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126891 RingCT/type: yes/0
Extra: 01d09b364841e8663703466f9cf17a95a4152f02f1f7b980e96e18bf2c77d7c7070211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e12029bbe8e74921275458d60d9efceefd8534f08290a623566bb5679cf6842c 0.600000000000 1632742 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": 1148017, "vin": [ { "gen": { "height": 1148007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e12029bbe8e74921275458d60d9efceefd8534f08290a623566bb5679cf6842c" } } ], "extra": [ 1, 208, 155, 54, 72, 65, 232, 102, 55, 3, 70, 111, 156, 241, 122, 149, 164, 21, 47, 2, 241, 247, 185, 128, 233, 110, 24, 191, 44, 119, 215, 199, 7, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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