Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2724e996953e95b18324ff9be1e67a927e717c6bd6006ea269be6687159b31b2

Tx prefix hash: b98a51abe37c6840b165d1de12273841a2541d8e40e31bc3abce49a4b426eef0
Tx public key: 9d26a597cb22fea962ca791299dd82a291156bcd5a6a6f0896a4f5bebe9caed9
Timestamp: 1706413855 Timestamp [UCT]: 2024-01-28 03:50:55 Age [y:d:h:m:s]: 01:098:07:56:10
Block: 944898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331379 RingCT/type: yes/0
Extra: 019d26a597cb22fea962ca791299dd82a291156bcd5a6a6f0896a4f5bebe9caed902110000000310a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5cd5cc3605722adef7c0c1330ce48a21964a064dcc776925b75fdf1bee327a3 0.600000000000 1403194 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": 944908, "vin": [ { "gen": { "height": 944898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5cd5cc3605722adef7c0c1330ce48a21964a064dcc776925b75fdf1bee327a3" } } ], "extra": [ 1, 157, 38, 165, 151, 203, 34, 254, 169, 98, 202, 121, 18, 153, 221, 130, 162, 145, 21, 107, 205, 90, 106, 111, 8, 150, 164, 245, 190, 190, 156, 174, 217, 2, 17, 0, 0, 0, 3, 16, 161, 116, 143, 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