Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33174ec3e7f7fe73ae62e994d0764b51277e77cba4c9ce4a05fd4a404595d7e

Tx prefix hash: bccaddde1ab3debd41f8d166de7e176b7a399563301fa0bf61cf4f33e865e126
Tx public key: a99d65224f522ec1f8df777ec1d740b12fbeb1defcf8f69e2b27a48d76c58f81
Timestamp: 1700991780 Timestamp [UCT]: 2023-11-26 09:43:00 Age [y:d:h:m:s]: 01:169:08:20:59
Block: 899964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382231 RingCT/type: yes/0
Extra: 01a99d65224f522ec1f8df777ec1d740b12fbeb1defcf8f69e2b27a48d76c58f81021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.639802096000 dcy

stealth address amount amount idx
00: 2dd1c427fc7135cf84108d5b705aa9ce20a954d08bd40e08e662f8d16d32d16b 0.639802096000 1356435 of 0

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": 899974, "vin": [ { "gen": { "height": 899964 } } ], "vout": [ { "amount": 639802096, "target": { "key": "2dd1c427fc7135cf84108d5b705aa9ce20a954d08bd40e08e662f8d16d32d16b" } } ], "extra": [ 1, 169, 157, 101, 34, 79, 82, 46, 193, 248, 223, 119, 126, 193, 215, 64, 177, 47, 190, 177, 222, 252, 248, 246, 158, 43, 39, 164, 141, 118, 197, 143, 129, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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