Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd112c0217f52585141a4f77a6a08c5e755e61bdf6cc64f3c969f119ab7b99f8

Tx prefix hash: ff4932e34e8a5854cf1bccb9e1e78423645162ae35a98d7bf7a3670078b843d3
Tx public key: 4926dfe5f773d4c1e4686c057befaa6985750221138433e057bb8d443728a373
Timestamp: 1710729655 Timestamp [UCT]: 2024-03-18 02:40:55 Age [y:d:h:m:s]: 01:008:01:17:34
Block: 980721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266698 RingCT/type: yes/0
Extra: 014926dfe5f773d4c1e4686c057befaa6985750221138433e057bb8d443728a37302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77969ee09d3f375b20f538a6f842f6770c8a9e9b959c6ddc1bf172e06d18b5f4 0.600000000000 1440802 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": 980731, "vin": [ { "gen": { "height": 980721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77969ee09d3f375b20f538a6f842f6770c8a9e9b959c6ddc1bf172e06d18b5f4" } } ], "extra": [ 1, 73, 38, 223, 229, 247, 115, 212, 193, 228, 104, 108, 5, 123, 239, 170, 105, 133, 117, 2, 33, 19, 132, 51, 224, 87, 187, 141, 68, 55, 40, 163, 115, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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