Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7fd733a46b6e616d4987ed1ea0c49634b60ad4a12a6c7666d79f28629828905

Tx prefix hash: 03a0b8bd96c6d61c0cb6cdfc9edf52c529de69df0cf8a5998271559a3f552452
Tx public key: 17bcfb8563d1c770cf53df6fcdbe6a19dfac9cf842d0b1f82b10dfb64907614d
Timestamp: 1625417944 Timestamp [UCT]: 2021-07-04 16:59:04 Age [y:d:h:m:s]: 03:178:22:50:18
Block: 288238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 897574 RingCT/type: yes/0
Extra: 0117bcfb8563d1c770cf53df6fcdbe6a19dfac9cf842d0b1f82b10dfb64907614d021100000048bffe00bb000000000000000000

1 output(s) for total of 68.070021671000 dcy

stealth address amount amount idx
00: 2fcbdd0dbc420729e0f0ed67131e624b02868fb0c7d22a152ae542c496b5e7c9 68.070021671000 603949 of 0

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": 288248, "vin": [ { "gen": { "height": 288238 } } ], "vout": [ { "amount": 68070021671, "target": { "key": "2fcbdd0dbc420729e0f0ed67131e624b02868fb0c7d22a152ae542c496b5e7c9" } } ], "extra": [ 1, 23, 188, 251, 133, 99, 209, 199, 112, 207, 83, 223, 111, 205, 190, 106, 25, 223, 172, 156, 248, 66, 208, 177, 248, 43, 16, 223, 182, 73, 7, 97, 77, 2, 17, 0, 0, 0, 72, 191, 254, 0, 187, 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