Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f65eae32d86141eb2a59ed357e7194de28f751765913c64c30bdab49f54d6658

Tx prefix hash: 1364eb34ef0e979a0810bd105f636df2e13807bd9a032e2263667d6d3cadb4ef
Tx public key: b08b7cf9e727f2e4b030d61a3755f8dbac63b1e68ce8758609b186f20f2529c1
Timestamp: 1721174733 Timestamp [UCT]: 2024-07-17 00:05:33 Age [y:d:h:m:s]: 00:267:07:11:10
Block: 1067308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190958 RingCT/type: yes/0
Extra: 01b08b7cf9e727f2e4b030d61a3755f8dbac63b1e68ce8758609b186f20f2529c1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d8934af2d9ec015a7aeb44c7a49f8e4e2d0dc39c0858669a184c2490833aab1 0.600000000000 1538085 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": 1067318, "vin": [ { "gen": { "height": 1067308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d8934af2d9ec015a7aeb44c7a49f8e4e2d0dc39c0858669a184c2490833aab1" } } ], "extra": [ 1, 176, 139, 124, 249, 231, 39, 242, 228, 176, 48, 214, 26, 55, 85, 248, 219, 172, 99, 177, 230, 140, 232, 117, 134, 9, 177, 134, 242, 15, 37, 41, 193, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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