Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ae22650883e7db9d5caf5bc44bb8276f7575e6106c715cdb90ec532d511e1b

Tx prefix hash: 154300068e41b636e1974cf74ad4c8b70db5a2a35321ec35a562b5342285d2b3
Tx public key: ed7b60405a31ef2144d4a6d2bddd877ba1eadb762269cd6eaa6fc68d860fd652
Timestamp: 1705377128 Timestamp [UCT]: 2024-01-16 03:52:08 Age [y:d:h:m:s]: 01:093:01:20:40
Block: 936303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327616 RingCT/type: yes/0
Extra: 01ed7b60405a31ef2144d4a6d2bddd877ba1eadb762269cd6eaa6fc68d860fd65202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3464ceb7329863fc5a5a3bc7dd4048f68ef432a46c7c6eac7d32435e7964f6f0 0.600000000000 1394327 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": 936313, "vin": [ { "gen": { "height": 936303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3464ceb7329863fc5a5a3bc7dd4048f68ef432a46c7c6eac7d32435e7964f6f0" } } ], "extra": [ 1, 237, 123, 96, 64, 90, 49, 239, 33, 68, 212, 166, 210, 189, 221, 135, 123, 161, 234, 219, 118, 34, 105, 205, 110, 170, 111, 198, 141, 134, 15, 214, 82, 2, 17, 0, 0, 0, 1, 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