Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 680c2995e2d7747093ce083444470661890846b60d8b9175f42c7ca8cd9bba82

Tx prefix hash: 3bece9c6fa836bfc0daa47fd8f3a6f60170aa6985439ccbab5f8325c6303352c
Tx public key: ed57c558646dc64cfc4168f2a5d62a93cd9708a6a32ec9086a34459d8839a908
Timestamp: 1734076627 Timestamp [UCT]: 2024-12-13 07:57:07 Age [y:d:h:m:s]: 00:096:03:41:50
Block: 1174176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68500 RingCT/type: yes/0
Extra: 01ed57c558646dc64cfc4168f2a5d62a93cd9708a6a32ec9086a34459d8839a908021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cff016d6d80a39a6a7c23bfa4ad40245e5f28eafd873d2dfc024b82d0f8a1be5 0.600000000000 1660293 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": 1174186, "vin": [ { "gen": { "height": 1174176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cff016d6d80a39a6a7c23bfa4ad40245e5f28eafd873d2dfc024b82d0f8a1be5" } } ], "extra": [ 1, 237, 87, 197, 88, 100, 109, 198, 76, 252, 65, 104, 242, 165, 214, 42, 147, 205, 151, 8, 166, 163, 46, 201, 8, 106, 52, 69, 157, 136, 57, 169, 8, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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