Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff7d0f0ff20bef108239fb67fc1cdc7562851a3957ef899496dd842b34acff72

Tx prefix hash: 70414642c9a587a9cf70284260df7c6d3d9edf108cc3922ae9d7fcb6270bfc4b
Tx public key: 5580a38c8379fd4692a15bdb0b2d773b8d2a3a382576bdfec518638f85b6b753
Timestamp: 1713238350 Timestamp [UCT]: 2024-04-16 03:32:30 Age [y:d:h:m:s]: 01:031:17:34:02
Block: 1001488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283645 RingCT/type: yes/0
Extra: 015580a38c8379fd4692a15bdb0b2d773b8d2a3a382576bdfec518638f85b6b7530211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3083296b0e7d08d332feba3d4e776d90d1916eceeec15e20913604f55a1dde88 0.600000000000 1461992 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": 1001498, "vin": [ { "gen": { "height": 1001488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3083296b0e7d08d332feba3d4e776d90d1916eceeec15e20913604f55a1dde88" } } ], "extra": [ 1, 85, 128, 163, 140, 131, 121, 253, 70, 146, 161, 91, 219, 11, 45, 119, 59, 141, 42, 58, 56, 37, 118, 189, 254, 197, 24, 99, 143, 133, 182, 183, 83, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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