Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdd57b397a1a61d89e880ec3825c8f4eac47cdf3821fceea684b6caaae0978ce

Tx prefix hash: 54f12e36a1f6d2e7a849fb5b29bc6d1af8ae68faecfcab8a82353bf9b2ac27f6
Tx public key: e0ad09d2d932cd02d98b2bec2199295680bcc5afdb2f201c2e59e747f2016cd2
Timestamp: 1719788584 Timestamp [UCT]: 2024-06-30 23:03:04 Age [y:d:h:m:s]: 01:132:08:34:35
Block: 1055795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353142 RingCT/type: yes/0
Extra: 01e0ad09d2d932cd02d98b2bec2199295680bcc5afdb2f201c2e59e747f2016cd20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b5df73c0087a45f6d14e3679196a759b8f1e2030b941618203acdac74b6f5ea 0.600000000000 1526200 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": 1055805, "vin": [ { "gen": { "height": 1055795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b5df73c0087a45f6d14e3679196a759b8f1e2030b941618203acdac74b6f5ea" } } ], "extra": [ 1, 224, 173, 9, 210, 217, 50, 205, 2, 217, 139, 43, 236, 33, 153, 41, 86, 128, 188, 197, 175, 219, 47, 32, 28, 46, 89, 231, 71, 242, 1, 108, 210, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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