Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 875047fc6787b40bb7c643ea23149f72dfd090e7b3f1bb3a48a5e59db3d55258

Tx prefix hash: 67d6a17fc1315af2f609c585dc60568a4ecba7052d22b53121a94b6a5ece1cf6
Tx public key: 8fed8503a78d4eeec065420814c47cc40fec83c3b22b531d59fd95c2000cb3a2
Timestamp: 1707194913 Timestamp [UCT]: 2024-02-06 04:48:33 Age [y:d:h:m:s]: 01:022:13:54:11
Block: 951382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277163 RingCT/type: yes/0
Extra: 018fed8503a78d4eeec065420814c47cc40fec83c3b22b531d59fd95c2000cb3a202110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a65b92c6a3c80be0161f7e3e419c1bbeffdcd6f07d5efe157cae932c3997d71 0.600000000000 1410140 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": 951392, "vin": [ { "gen": { "height": 951382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a65b92c6a3c80be0161f7e3e419c1bbeffdcd6f07d5efe157cae932c3997d71" } } ], "extra": [ 1, 143, 237, 133, 3, 167, 141, 78, 238, 192, 101, 66, 8, 20, 196, 124, 196, 15, 236, 131, 195, 178, 43, 83, 29, 89, 253, 149, 194, 0, 12, 179, 162, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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