Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e860f8727aa4582510ccfb1a179241ad4033ae6357b232a2c7282e19747c7e09

Tx prefix hash: e9bf0091623d6dab5f33dc54fae97a5a1ef2c55256b7f3692b01abe7cdf679cf
Tx public key: 236eecccb767671ceb719e05f6dda61844c0318f3ca8cdbbe1da7d3cbe736058
Timestamp: 1703051347 Timestamp [UCT]: 2023-12-20 05:49:07 Age [y:d:h:m:s]: 01:126:20:56:53
Block: 917044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351818 RingCT/type: yes/0
Extra: 01236eecccb767671ceb719e05f6dda61844c0318f3ca8cdbbe1da7d3cbe73605802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1607c6c40220036417e093e6de44fb1d03b9f1a731c3e34bf9b2c4472a0e43bd 0.600000000000 1374608 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": 917054, "vin": [ { "gen": { "height": 917044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1607c6c40220036417e093e6de44fb1d03b9f1a731c3e34bf9b2c4472a0e43bd" } } ], "extra": [ 1, 35, 110, 236, 204, 183, 103, 103, 28, 235, 113, 158, 5, 246, 221, 166, 24, 68, 192, 49, 143, 60, 168, 205, 187, 225, 218, 125, 60, 190, 115, 96, 88, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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