Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ae3f33452d6f133488537f3f847e3f3ed7de191f38379d70635e80e55944c9

Tx prefix hash: 2de88d2f64fe5e2dc2282ff8bda2252e12e4467e35f40909ff0429d971b2839d
Tx public key: 86c7bee50a2ee343dc253113d665e9eba1c2f4cfb22e6f243370121845b948df
Timestamp: 1717724146 Timestamp [UCT]: 2024-06-07 01:35:46 Age [y:d:h:m:s]: 00:281:21:42:34
Block: 1038689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201483 RingCT/type: yes/0
Extra: 0186c7bee50a2ee343dc253113d665e9eba1c2f4cfb22e6f243370121845b948df0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd3a89d1b5bd577504a6df8ad10d6b2d0feef61e53e42ca3fea7f70a8cee4685 0.600000000000 1507250 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": 1038699, "vin": [ { "gen": { "height": 1038689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd3a89d1b5bd577504a6df8ad10d6b2d0feef61e53e42ca3fea7f70a8cee4685" } } ], "extra": [ 1, 134, 199, 190, 229, 10, 46, 227, 67, 220, 37, 49, 19, 214, 101, 233, 235, 161, 194, 244, 207, 178, 46, 111, 36, 51, 112, 18, 24, 69, 185, 72, 223, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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