Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e778ff3f66a15492040b16e3982a6a8567c73f1ade5189e29dfa9c477be04019

Tx prefix hash: f409f202654aad145f3fac13a7844af1c5d0abab517e50ce9fd7312fd7cbb10e
Tx public key: 431ad6d6194e6ea7b1b4481e084d64388573086baa6e8d9cbea3133984e91593
Timestamp: 1730941863 Timestamp [UCT]: 2024-11-07 01:11:03 Age [y:d:h:m:s]: 00:139:01:17:39
Block: 1148182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99195 RingCT/type: yes/0
Extra: 01431ad6d6194e6ea7b1b4481e084d64388573086baa6e8d9cbea3133984e9159302110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0726330df5b3a941be9c4d303be3634314fb163876b817e47d878556ddf9ac13 0.600000000000 1632969 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": 1148192, "vin": [ { "gen": { "height": 1148182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0726330df5b3a941be9c4d303be3634314fb163876b817e47d878556ddf9ac13" } } ], "extra": [ 1, 67, 26, 214, 214, 25, 78, 110, 167, 177, 180, 72, 30, 8, 77, 100, 56, 133, 115, 8, 107, 170, 110, 141, 156, 190, 163, 19, 57, 132, 233, 21, 147, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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