Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 626213b37d39e8b05e44e3d910b47743841f5aa769b8df415b25db32c1a8fe50

Tx prefix hash: d6a27f3e74948e1724cb7a47f96a255b6a00564a0f81791193db8f330712666e
Tx public key: df4d688ffadcb13be7de2a2c20c4b52564009ce564129d20f65313fb1cdd137d
Timestamp: 1706419637 Timestamp [UCT]: 2024-01-28 05:27:17 Age [y:d:h:m:s]: 00:291:20:03:32
Block: 944946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208969 RingCT/type: yes/0
Extra: 01df4d688ffadcb13be7de2a2c20c4b52564009ce564129d20f65313fb1cdd137d02110000000281d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a3681cc535adb3e1dd64c16aee27a888eca1a2ca4e2a690af683c1cf1a65da0 0.600000000000 1403246 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": 944956, "vin": [ { "gen": { "height": 944946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a3681cc535adb3e1dd64c16aee27a888eca1a2ca4e2a690af683c1cf1a65da0" } } ], "extra": [ 1, 223, 77, 104, 143, 250, 220, 177, 59, 231, 222, 42, 44, 32, 196, 181, 37, 100, 0, 156, 229, 100, 18, 157, 32, 246, 83, 19, 251, 28, 221, 19, 125, 2, 17, 0, 0, 0, 2, 129, 215, 29, 85, 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