Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1bc247bbb3938cc56e456c9d7beeadb4696417cecb41294df0f2bc8da65d3b3

Tx prefix hash: a6985eada8171b2f8093c96678d80a270cc23456b6bac50f7b3ada279b391f18
Tx public key: 9b718be279181d9d1d799859f7db30a6f1a50b14f3dadbf9603e825f7bab9e45
Timestamp: 1725527207 Timestamp [UCT]: 2024-09-05 09:06:47 Age [y:d:h:m:s]: 00:251:23:54:40
Block: 1103377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179974 RingCT/type: yes/0
Extra: 019b718be279181d9d1d799859f7db30a6f1a50b14f3dadbf9603e825f7bab9e45021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ccab61526f25497de1fc6d2dfebd493e29ecda55635d85ec5c9a2e8a794a824 0.600000000000 1580184 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": 1103387, "vin": [ { "gen": { "height": 1103377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ccab61526f25497de1fc6d2dfebd493e29ecda55635d85ec5c9a2e8a794a824" } } ], "extra": [ 1, 155, 113, 139, 226, 121, 24, 29, 157, 29, 121, 152, 89, 247, 219, 48, 166, 241, 165, 11, 20, 243, 218, 219, 249, 96, 62, 130, 95, 123, 171, 158, 69, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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