Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f37e7eb4997a574e4daa3b451db88741426ccddca4e52c2a096e2f0b435e208

Tx prefix hash: ce15fec446fa06d1f133d92c202911d66bdcf3aebf9061be7a9dfe0ecebf494c
Tx public key: 867a1b40b083a96cb118ffa52fd2abc030f956c165db3fbf76aea8df0ac38957
Timestamp: 1714020706 Timestamp [UCT]: 2024-04-25 04:51:46 Age [y:d:h:m:s]: 00:349:06:53:44
Block: 1007975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249709 RingCT/type: yes/0
Extra: 01867a1b40b083a96cb118ffa52fd2abc030f956c165db3fbf76aea8df0ac389570211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f907be8fd597ebbe586d88842f6f69ddd69c0e7ccb54c652e460497add8e4c2 0.600000000000 1469441 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": 1007985, "vin": [ { "gen": { "height": 1007975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f907be8fd597ebbe586d88842f6f69ddd69c0e7ccb54c652e460497add8e4c2" } } ], "extra": [ 1, 134, 122, 27, 64, 176, 131, 169, 108, 177, 24, 255, 165, 47, 210, 171, 192, 48, 249, 86, 193, 101, 219, 63, 191, 118, 174, 168, 223, 10, 195, 137, 87, 2, 17, 0, 0, 0, 2, 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