Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e5e43fcf37d242aaf6cddb0a6c35f4a00d17ce7a1af08c385abc1fbf241466d

Tx prefix hash: 4921b09918dabdf60fb644b737f2927e17fd6cc1c99a010dd64d2568412eb7ac
Tx public key: ba33970c029a376fc3f723ba5e504cff844ebd9a6151dd3953a4218e450b7bc4
Timestamp: 1702867132 Timestamp [UCT]: 2023-12-18 02:38:52 Age [y:d:h:m:s]: 01:149:16:03:03
Block: 915513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368120 RingCT/type: yes/0
Extra: 01ba33970c029a376fc3f723ba5e504cff844ebd9a6151dd3953a4218e450b7bc4021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29054c3bda9d1a22fdf93b94e84381b6c90c8f8be39f5c73355ab98063542e25 0.600000000000 1372909 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": 915523, "vin": [ { "gen": { "height": 915513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29054c3bda9d1a22fdf93b94e84381b6c90c8f8be39f5c73355ab98063542e25" } } ], "extra": [ 1, 186, 51, 151, 12, 2, 154, 55, 111, 195, 247, 35, 186, 94, 80, 76, 255, 132, 78, 189, 154, 97, 81, 221, 57, 83, 164, 33, 142, 69, 11, 123, 196, 2, 17, 0, 0, 0, 1, 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