Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18f29e7383c19390ae8258cddc5346a298e16652cc7fb241ee1a4c7650e234e3

Tx prefix hash: dc7cd83970d671b4520276db5149ed23d018e211fd3c6bd01cfe56643a644b1d
Tx public key: f1443ff46db456aa27c5050832e3d2d434b00c7c95a5e2a8d0319128decbb44d
Timestamp: 1706638380 Timestamp [UCT]: 2024-01-30 18:13:00 Age [y:d:h:m:s]: 01:069:10:23:42
Block: 946756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310702 RingCT/type: yes/0
Extra: 01f1443ff46db456aa27c5050832e3d2d434b00c7c95a5e2a8d0319128decbb44d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d56f6e090dbc34a1d3d3e64122da03f20fb1d90e16f51b6880a2a0ead8629e9b 0.600000000000 1405096 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": 946766, "vin": [ { "gen": { "height": 946756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d56f6e090dbc34a1d3d3e64122da03f20fb1d90e16f51b6880a2a0ead8629e9b" } } ], "extra": [ 1, 241, 68, 63, 244, 109, 180, 86, 170, 39, 197, 5, 8, 50, 227, 210, 212, 52, 176, 12, 124, 149, 165, 226, 168, 208, 49, 145, 40, 222, 203, 180, 77, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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