Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18ee92525c4fbc34b94a5dc950134879e62eb042b092f1a003093a43c187483f

Tx prefix hash: 21dfa36cdde8d52a1b30e274d711b05ecff16b9db10ba883acb6268449fb1af6
Tx public key: 381c90ed70790b20c5b7a7e51b9e493aa73a39f2c4ff6255f3ad3d6f74e2eb27
Timestamp: 1696132922 Timestamp [UCT]: 2023-10-01 04:02:02 Age [y:d:h:m:s]: 01:184:19:42:53
Block: 859885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393132 RingCT/type: yes/0
Extra: 01381c90ed70790b20c5b7a7e51b9e493aa73a39f2c4ff6255f3ad3d6f74e2eb2702110000000233af99f4000000000000000000

1 output(s) for total of 0.868648516000 dcy

stealth address amount amount idx
00: 914c0a8cd4af9df02c0a6a8319711634796557bf0b6cc9aad9cb5c59574485e9 0.868648516000 1314135 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": 859895, "vin": [ { "gen": { "height": 859885 } } ], "vout": [ { "amount": 868648516, "target": { "key": "914c0a8cd4af9df02c0a6a8319711634796557bf0b6cc9aad9cb5c59574485e9" } } ], "extra": [ 1, 56, 28, 144, 237, 112, 121, 11, 32, 197, 183, 167, 229, 27, 158, 73, 58, 167, 58, 57, 242, 196, 255, 98, 85, 243, 173, 61, 111, 116, 226, 235, 39, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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