Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d734f3647b2d03c9b2d2c8e713f458a86d795bf6976998751ef52b4906e025dc

Tx prefix hash: 7d029ab6bc3dc05d8e49c752b2d165ee4b3574dba4e20512aa5546868d5adcfd
Tx public key: 8e07b0945b4a7149446c5f749a3a62615017691dafeb5e75118c084237c98f35
Timestamp: 1733154323 Timestamp [UCT]: 2024-12-02 15:45:23 Age [y:d:h:m:s]: 00:111:22:56:33
Block: 1166510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79813 RingCT/type: yes/0
Extra: 018e07b0945b4a7149446c5f749a3a62615017691dafeb5e75118c084237c98f35021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 719d3eeb0e372a127c075a4417be7293258f959389a517ad88dd26e2f0473ed1 0.600000000000 1652197 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": 1166520, "vin": [ { "gen": { "height": 1166510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "719d3eeb0e372a127c075a4417be7293258f959389a517ad88dd26e2f0473ed1" } } ], "extra": [ 1, 142, 7, 176, 148, 91, 74, 113, 73, 68, 108, 95, 116, 154, 58, 98, 97, 80, 23, 105, 29, 175, 235, 94, 117, 17, 140, 8, 66, 55, 201, 143, 53, 2, 17, 0, 0, 0, 4, 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