Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c5294bc5e99d1b979f8700713c39a4397f2d182f374b3b726421af69d3ef782

Tx prefix hash: 392242e697f2a5e3f7fe20d65c1c5594e753a72a9c04ae066528cebbcd85ea86
Tx public key: a894612939ddad8942d9a92d745b8080e4e1787da123794a60f1a40bc6c14fd7
Timestamp: 1727130460 Timestamp [UCT]: 2024-09-23 22:27:40 Age [y:d:h:m:s]: 00:122:10:22:28
Block: 1116676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87495 RingCT/type: yes/0
Extra: 01a894612939ddad8942d9a92d745b8080e4e1787da123794a60f1a40bc6c14fd7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1557d856158f10dffae829b9cb4499a6c676a9700f3e66ae5aacff176f271b3b 0.600000000000 1597241 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": 1116686, "vin": [ { "gen": { "height": 1116676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1557d856158f10dffae829b9cb4499a6c676a9700f3e66ae5aacff176f271b3b" } } ], "extra": [ 1, 168, 148, 97, 41, 57, 221, 173, 137, 66, 217, 169, 45, 116, 91, 128, 128, 228, 225, 120, 125, 161, 35, 121, 74, 96, 241, 164, 11, 198, 193, 79, 215, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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