Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb510c37389b1be14e632a1e37cb55fc2014e0275b6bb9478cb27c7bc2b34091

Tx prefix hash: 0a6b25f03b70ab352ef23f23734239d30c9a32b522f2d369090a07463a2965b4
Tx public key: dd0f5a00dcb24d0a6b454a2932801990ecab91f894f39a1f1170ac1247eaf1e4
Timestamp: 1643316095 Timestamp [UCT]: 2022-01-27 20:41:35 Age [y:d:h:m:s]: 03:139:15:38:36
Block: 426587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 878937 RingCT/type: yes/0
Extra: 01dd0f5a00dcb24d0a6b454a2932801990ecab91f894f39a1f1170ac1247eaf1e40211000000034a0f5013000000000000000000

1 output(s) for total of 23.688660151000 dcy

stealth address amount amount idx
00: db517eee7bacc758a47bc151492e568d77f5b020a81446fbc2172a507abfb704 23.688660151000 835434 of 0

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": 426597, "vin": [ { "gen": { "height": 426587 } } ], "vout": [ { "amount": 23688660151, "target": { "key": "db517eee7bacc758a47bc151492e568d77f5b020a81446fbc2172a507abfb704" } } ], "extra": [ 1, 221, 15, 90, 0, 220, 178, 77, 10, 107, 69, 74, 41, 50, 128, 25, 144, 236, 171, 145, 248, 148, 243, 154, 31, 17, 112, 172, 18, 71, 234, 241, 228, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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