Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 767fdec104a73e3b0c1597ec5826179e920194ef291b863f37b6f6b4efe36045

Tx prefix hash: d99f3bbd5380baa59a01dd2075b7d6716c59995669f7a3d95c7bd1d115d3b409
Tx public key: 8940e8f38c999b30c9988a799dec7e82189480ba384cb81493c5d611e40ad04a
Timestamp: 1703068043 Timestamp [UCT]: 2023-12-20 10:27:23 Age [y:d:h:m:s]: 01:329:18:18:35
Block: 917181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494531 RingCT/type: yes/0
Extra: 018940e8f38c999b30c9988a799dec7e82189480ba384cb81493c5d611e40ad04a021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a95c96c014730d5d4e2c08cb9d0adeff6278e4fe9aafae2f835015d2c4fb0cb9 0.600000000000 1374751 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": 917191, "vin": [ { "gen": { "height": 917181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a95c96c014730d5d4e2c08cb9d0adeff6278e4fe9aafae2f835015d2c4fb0cb9" } } ], "extra": [ 1, 137, 64, 232, 243, 140, 153, 155, 48, 201, 152, 138, 121, 157, 236, 126, 130, 24, 148, 128, 186, 56, 76, 184, 20, 147, 197, 214, 17, 228, 10, 208, 74, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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