Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac242da5367f44c62f87ddfc30b90976dbf3e92aeb058d1e86e607ac312187a

Tx prefix hash: ff7ada2e66bc7d03d32b3289608393ebc071e0c38f762d081da170b28394a23c
Tx public key: d7a91aa88a0f160762248368bb48ae753f02433a99a29b48dd67379c59f0ae0a
Timestamp: 1715032831 Timestamp [UCT]: 2024-05-06 22:00:31 Age [y:d:h:m:s]: 00:138:01:34:52
Block: 1016379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98893 RingCT/type: yes/0
Extra: 01d7a91aa88a0f160762248368bb48ae753f02433a99a29b48dd67379c59f0ae0a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32fcf12db231f804b1d4e321089a7d612d824f2785dca4b47807ab3b0c0aa561 0.600000000000 1479946 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": 1016389, "vin": [ { "gen": { "height": 1016379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32fcf12db231f804b1d4e321089a7d612d824f2785dca4b47807ab3b0c0aa561" } } ], "extra": [ 1, 215, 169, 26, 168, 138, 15, 22, 7, 98, 36, 131, 104, 187, 72, 174, 117, 63, 2, 67, 58, 153, 162, 155, 72, 221, 103, 55, 156, 89, 240, 174, 10, 2, 17, 0, 0, 0, 1, 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