Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4a72caf820bce5c9ef0cd0697a7d3d809cd86a4136b5998cf9d85fa351c63d

Tx prefix hash: e1a07834798f0a78a5434cdb045adecd993984d3c3d25f32e27d22ab0fea19e4
Tx public key: f27f7e60442abf397c70e6af08ce7012e5814592ba6fe1649fcd4f3017d4e4e3
Timestamp: 1709507472 Timestamp [UCT]: 2024-03-03 23:11:12 Age [y:d:h:m:s]: 01:248:19:10:39
Block: 970569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436537 RingCT/type: yes/0
Extra: 01f27f7e60442abf397c70e6af08ce7012e5814592ba6fe1649fcd4f3017d4e4e30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd7fb43dd8eeeb0712e7507c0cff05b21bfb534d053e4d55fb4aee9999e366fc 0.600000000000 1430428 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": 970579, "vin": [ { "gen": { "height": 970569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd7fb43dd8eeeb0712e7507c0cff05b21bfb534d053e4d55fb4aee9999e366fc" } } ], "extra": [ 1, 242, 127, 126, 96, 68, 42, 191, 57, 124, 112, 230, 175, 8, 206, 112, 18, 229, 129, 69, 146, 186, 111, 225, 100, 159, 205, 79, 48, 23, 212, 228, 227, 2, 17, 0, 0, 0, 4, 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