Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119cdfa5872b76fd118be64e317ceb8ba9332a52306a567d19a6db3492419845

Tx prefix hash: 39a2c74b87c818664a1db6437529a1759172e906632439b7acff3da3fbe61d62
Tx public key: d259ae82f81b3b39bad8c527985e59f5154a48865970e6a76e4a74a81c775c4b
Timestamp: 1731176636 Timestamp [UCT]: 2024-11-09 18:23:56 Age [y:d:h:m:s]: 00:018:10:25:40
Block: 1150131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13190 RingCT/type: yes/0
Extra: 01d259ae82f81b3b39bad8c527985e59f5154a48865970e6a76e4a74a81c775c4b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1d1b3fbdd81b43dbcdb779a4799a5b7c3f4ed2fc6d97e83d1c8aff71bd0cf87 0.600000000000 1635348 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": 1150141, "vin": [ { "gen": { "height": 1150131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1d1b3fbdd81b43dbcdb779a4799a5b7c3f4ed2fc6d97e83d1c8aff71bd0cf87" } } ], "extra": [ 1, 210, 89, 174, 130, 248, 27, 59, 57, 186, 216, 197, 39, 152, 94, 89, 245, 21, 74, 72, 134, 89, 112, 230, 167, 110, 74, 116, 168, 28, 119, 92, 75, 2, 17, 0, 0, 0, 1, 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