Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97b02ac1991953647d17faaea75f11dadf1c27f457898ff56667a629097b18b8

Tx prefix hash: e7bc0bf9f990a6ca80fc7c0b604261eb95af8f8a9f2e5ddb9bb546d19823e462
Tx public key: 0b369ccb9c03375691eb9954db3cb761bb9bc9321dc973ab4a373c259cd85a1f
Timestamp: 1712457551 Timestamp [UCT]: 2024-04-07 02:39:11 Age [y:d:h:m:s]: 00:361:10:50:32
Block: 994990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258448 RingCT/type: yes/0
Extra: 010b369ccb9c03375691eb9954db3cb761bb9bc9321dc973ab4a373c259cd85a1f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43392983692e9cc61e0f7336141287b2c9fdff3e8f63cc00f4dc6c8b688cc4d2 0.600000000000 1455394 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": 995000, "vin": [ { "gen": { "height": 994990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43392983692e9cc61e0f7336141287b2c9fdff3e8f63cc00f4dc6c8b688cc4d2" } } ], "extra": [ 1, 11, 54, 156, 203, 156, 3, 55, 86, 145, 235, 153, 84, 219, 60, 183, 97, 187, 155, 201, 50, 29, 201, 115, 171, 74, 55, 60, 37, 156, 216, 90, 31, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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