Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad2727698de7a35e2b9e781c2adc8bf92ad1a67ac42dc234c0eafe91f68c57d0

Tx prefix hash: 30a53e7dee4e0fd8d62bbc5375c43ae8b590c058d03e9f75ccca5163c43b2493
Tx public key: 656b1fb4cbe25808aa4169e8db0ad16dde777cb9c0a0fb0afc0c864718a273a2
Timestamp: 1695456088 Timestamp [UCT]: 2023-09-23 08:01:28 Age [y:d:h:m:s]: 01:124:03:33:45
Block: 854268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349987 RingCT/type: yes/0
Extra: 01656b1fb4cbe25808aa4169e8db0ad16dde777cb9c0a0fb0afc0c864718a273a2021100000009faf35c9c000000000000000000

1 output(s) for total of 0.906683146000 dcy

stealth address amount amount idx
00: fbe131150d7ba770aa4732ceadb894df0f999f6e0ef48f9861589b885989fabf 0.906683146000 1308234 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": 854278, "vin": [ { "gen": { "height": 854268 } } ], "vout": [ { "amount": 906683146, "target": { "key": "fbe131150d7ba770aa4732ceadb894df0f999f6e0ef48f9861589b885989fabf" } } ], "extra": [ 1, 101, 107, 31, 180, 203, 226, 88, 8, 170, 65, 105, 232, 219, 10, 209, 109, 222, 119, 124, 185, 192, 160, 251, 10, 252, 12, 134, 71, 24, 162, 115, 162, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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