Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb49bda1d48a6d5d8c940d956ea522e7cd093d097cf2c6ddae77beca0c2197c4

Tx prefix hash: f3457bbf75f9c88237f118913024c95c00decb6d229073bbc07fc16a4b27c838
Tx public key: 3e936380ac0f9ae7157546ed9239f1a33e7cedb245c8d36a6cecf224a1f3441d
Timestamp: 1703368788 Timestamp [UCT]: 2023-12-23 21:59:48 Age [y:d:h:m:s]: 01:344:15:30:06
Block: 919670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505191 RingCT/type: yes/0
Extra: 013e936380ac0f9ae7157546ed9239f1a33e7cedb245c8d36a6cecf224a1f3441d02110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 169090cea6230232ac13a71ac44394734b304dc4739260aa56cde786770192d4 0.600000000000 1377346 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": 919680, "vin": [ { "gen": { "height": 919670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "169090cea6230232ac13a71ac44394734b304dc4739260aa56cde786770192d4" } } ], "extra": [ 1, 62, 147, 99, 128, 172, 15, 154, 231, 21, 117, 70, 237, 146, 57, 241, 163, 62, 124, 237, 178, 69, 200, 211, 106, 108, 236, 242, 36, 161, 243, 68, 29, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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