Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa88c6bafe75958d3ce7dc7a99c505200917fe38c7bc5d885023a06b121039b

Tx prefix hash: fbe019d87f40141bc7024f77cc7d33f7706184d3a5f498087f4c474aff4356bd
Tx public key: 1460a8ae88f4d405fe3fd9e5a81676899ea153e1ce2e5af3294dfce308d1671c
Timestamp: 1738834480 Timestamp [UCT]: 2025-02-06 09:34:40 Age [y:d:h:m:s]: 00:288:11:44:55
Block: 1213271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203943 RingCT/type: yes/0
Extra: 011460a8ae88f4d405fe3fd9e5a81676899ea153e1ce2e5af3294dfce308d1671c0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e1314b1172b03b38818440849a991ab2e37bb24a934eb59bde1ac98f331e046 0.600000000000 1700050 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": 1213281, "vin": [ { "gen": { "height": 1213271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e1314b1172b03b38818440849a991ab2e37bb24a934eb59bde1ac98f331e046" } } ], "extra": [ 1, 20, 96, 168, 174, 136, 244, 212, 5, 254, 63, 217, 229, 168, 22, 118, 137, 158, 161, 83, 225, 206, 46, 90, 243, 41, 77, 252, 227, 8, 209, 103, 28, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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