Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97f4b833854e2e2f8f37a8c68e2fd6d7aa9c9bd89379c50b544a031c3cd2864a

Tx prefix hash: 068a91b2b9be72426518e0a63e3c0eb5fd61f927b2403ccc2f9c0fdedc3ed31b
Tx public key: 296cf6385256fd4348eb7f7535f4164b4e2e4f11b3d739326e5fa05d025eb2e5
Timestamp: 1732708470 Timestamp [UCT]: 2024-11-27 11:54:30 Age [y:d:h:m:s]: 00:132:21:34:16
Block: 1162822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94789 RingCT/type: yes/0
Extra: 01296cf6385256fd4348eb7f7535f4164b4e2e4f11b3d739326e5fa05d025eb2e5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41dbfb5f2f594ff9992b1e9c46621440f9810ad674d49f76d58c24bfd672b3b5 0.600000000000 1648485 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": 1162832, "vin": [ { "gen": { "height": 1162822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41dbfb5f2f594ff9992b1e9c46621440f9810ad674d49f76d58c24bfd672b3b5" } } ], "extra": [ 1, 41, 108, 246, 56, 82, 86, 253, 67, 72, 235, 127, 117, 53, 244, 22, 75, 78, 46, 79, 17, 179, 215, 57, 50, 110, 95, 160, 93, 2, 94, 178, 229, 2, 17, 0, 0, 0, 2, 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