Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf944ea23ea00e7830f4765f8ce10a942ccd231a49138bc74c70f0627c01f8bd

Tx prefix hash: 174291163363b1723970a775675c625886f353dc9f4649d6c5a144a040aaf9e4
Tx public key: e7c71f0fae48347e09e12acecb54daa761fd244d46c42e676a185c0f86684d7a
Timestamp: 1734476205 Timestamp [UCT]: 2024-12-17 22:56:45 Age [y:d:h:m:s]: 00:336:21:16:31
Block: 1177485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238267 RingCT/type: yes/0
Extra: 01e7c71f0fae48347e09e12acecb54daa761fd244d46c42e676a185c0f86684d7a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41fdefc125ad492fd1de53fe3428a816b3e77bf118a0fd7d64d1d5bca22fd837 0.600000000000 1663856 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": 1177495, "vin": [ { "gen": { "height": 1177485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41fdefc125ad492fd1de53fe3428a816b3e77bf118a0fd7d64d1d5bca22fd837" } } ], "extra": [ 1, 231, 199, 31, 15, 174, 72, 52, 126, 9, 225, 42, 206, 203, 84, 218, 167, 97, 253, 36, 77, 70, 196, 46, 103, 106, 24, 92, 15, 134, 104, 77, 122, 2, 17, 0, 0, 0, 2, 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