Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 434d316cfb95170e1b2e25d3e9d5fbe0f943f1dea88c26ae7d441ccafcb3ad6c

Tx prefix hash: 30c92713af722896ee17b38161a0aa800e3f6a02a6947d4ff525eaa712a5e464
Tx public key: 9d182926b9d9672034aa647e43f5315b2e3085c104e49a5edca268103a13701d
Timestamp: 1709466312 Timestamp [UCT]: 2024-03-03 11:45:12 Age [y:d:h:m:s]: 00:329:16:33:10
Block: 970234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235752 RingCT/type: yes/0
Extra: 019d182926b9d9672034aa647e43f5315b2e3085c104e49a5edca268103a13701d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8694ea615483b04672ed5307153c70e81d64dac64bfc9acf2becb8f2e10ee60 0.600000000000 1430085 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": 970244, "vin": [ { "gen": { "height": 970234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8694ea615483b04672ed5307153c70e81d64dac64bfc9acf2becb8f2e10ee60" } } ], "extra": [ 1, 157, 24, 41, 38, 185, 217, 103, 32, 52, 170, 100, 126, 67, 245, 49, 91, 46, 48, 133, 193, 4, 228, 154, 94, 220, 162, 104, 16, 58, 19, 112, 29, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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