Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e3e9ba275fa21bb2c2c6cd0ec74f99bd3409f36c0abe9d71d942e1b2cbaf9a

Tx prefix hash: 9ab7d686a084591bde27278a6098b2cee26299e1b988afb72bb24259704c228c
Tx public key: b0b3eedf3f9188f23491b402e998ea6e49df68a91da13294727ebefbdfd13b9b
Timestamp: 1706346396 Timestamp [UCT]: 2024-01-27 09:06:36 Age [y:d:h:m:s]: 01:084:23:49:48
Block: 944338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321830 RingCT/type: yes/0
Extra: 01b0b3eedf3f9188f23491b402e998ea6e49df68a91da13294727ebefbdfd13b9b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a53e36c953c90d4b33c9780d1ad8c2d41090e1e9211fd6a7f5c399b315c2c91b 0.600000000000 1402574 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": 944348, "vin": [ { "gen": { "height": 944338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a53e36c953c90d4b33c9780d1ad8c2d41090e1e9211fd6a7f5c399b315c2c91b" } } ], "extra": [ 1, 176, 179, 238, 223, 63, 145, 136, 242, 52, 145, 180, 2, 233, 152, 234, 110, 73, 223, 104, 169, 29, 161, 50, 148, 114, 126, 190, 251, 223, 209, 59, 155, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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