Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34777a19418ef58891d9b7e79461b49b8e20999f039ea01d3e534629e86b56cf

Tx prefix hash: d2f338998a6b7b262ac843adfeec49248f697fd3ca4513ff78b13d01d8fef378
Tx public key: 66b81f37db2d2c3d2dcc8eb91a70a4c88ed4037f9d5971f4a88ec4ae79a8e074
Timestamp: 1737405371 Timestamp [UCT]: 2025-01-20 20:36:11 Age [y:d:h:m:s]: 00:150:20:56:06
Block: 1201663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107531 RingCT/type: yes/0
Extra: 0166b81f37db2d2c3d2dcc8eb91a70a4c88ed4037f9d5971f4a88ec4ae79a8e074021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0bcc91589030f479602602ccffa8e0f5fba0203700e6d9528571ad662711873 0.600000000000 1688320 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": 1201673, "vin": [ { "gen": { "height": 1201663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0bcc91589030f479602602ccffa8e0f5fba0203700e6d9528571ad662711873" } } ], "extra": [ 1, 102, 184, 31, 55, 219, 45, 44, 61, 45, 204, 142, 185, 26, 112, 164, 200, 142, 212, 3, 127, 157, 89, 113, 244, 168, 142, 196, 174, 121, 168, 224, 116, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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