Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f92b51486911251d1482ed629e6d33115cb8253ba2ff95ef6557914df596b728

Tx prefix hash: dc3ad41d63bfe1181547dca23ee38bb4aeaf6a3f44e922b53eb739283f6a1d13
Tx public key: bd13415b645f987e02e61eea0655541d039bcd24811a4cf40a78256fb957d6a5
Timestamp: 1682528236 Timestamp [UCT]: 2023-04-26 16:57:16 Age [y:d:h:m:s]: 01:304:02:39:32
Block: 747145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478562 RingCT/type: yes/0
Extra: 01bd13415b645f987e02e61eea0655541d039bcd24811a4cf40a78256fb957d6a50211000000017e406890000000000000000000

1 output(s) for total of 2.053105941000 dcy

stealth address amount amount idx
00: e6a00b3ba968c545b84ef43702bc5f5af3a5f6bc9c5e6d50d8161213b86b69ae 2.053105941000 1194786 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": 747155, "vin": [ { "gen": { "height": 747145 } } ], "vout": [ { "amount": 2053105941, "target": { "key": "e6a00b3ba968c545b84ef43702bc5f5af3a5f6bc9c5e6d50d8161213b86b69ae" } } ], "extra": [ 1, 189, 19, 65, 91, 100, 95, 152, 126, 2, 230, 30, 234, 6, 85, 84, 29, 3, 155, 205, 36, 129, 26, 76, 244, 10, 120, 37, 111, 185, 87, 214, 165, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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