Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6c7ecec0b838b790891b921ba04e03e8d0738aa501edd07a0b03250f9163527

Tx prefix hash: 3874aaf4efc4e33a870bd55b25dc1c01f4aec930fbbc8327c17f4bdb28133493
Tx public key: 6e937d7a925a1d0e0db9b51ebe867d428acf1f7fc986beaada464ac9b46cbb43
Timestamp: 1718434674 Timestamp [UCT]: 2024-06-15 06:57:54 Age [y:d:h:m:s]: 00:223:16:06:10
Block: 1044589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160005 RingCT/type: yes/0
Extra: 016e937d7a925a1d0e0db9b51ebe867d428acf1f7fc986beaada464ac9b46cbb43021100000001cd63fb1b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7a86eac4142850e0a1d9228ea6bf0432965d819825d7094248578caa829fc98 0.600000000000 1513936 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": 1044599, "vin": [ { "gen": { "height": 1044589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7a86eac4142850e0a1d9228ea6bf0432965d819825d7094248578caa829fc98" } } ], "extra": [ 1, 110, 147, 125, 122, 146, 90, 29, 14, 13, 185, 181, 30, 190, 134, 125, 66, 138, 207, 31, 127, 201, 134, 190, 170, 218, 70, 74, 201, 180, 108, 187, 67, 2, 17, 0, 0, 0, 1, 205, 99, 251, 27, 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