Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bace6ee29aa392ae0059c2b29c4c24ebcd5879e45a7449f4fa3063f1557acfa

Tx prefix hash: c6c6fd7645df5ba6011447ad2aad406e34f7cfcde37b4f3787d578074620f23a
Tx public key: 4a5bf8f27adef71455e1cde23a91ca22f6f5684288db62878b08c21b5584d371
Timestamp: 1719258786 Timestamp [UCT]: 2024-06-24 19:53:06 Age [y:d:h:m:s]: 00:267:21:13:48
Block: 1051405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191434 RingCT/type: yes/0
Extra: 014a5bf8f27adef71455e1cde23a91ca22f6f5684288db62878b08c21b5584d3710211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb614e4a42db5f3062167bc77d2d2ae5b3e90da29c9e9d733a8b5316b1f57d8 0.600000000000 1521716 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": 1051415, "vin": [ { "gen": { "height": 1051405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb614e4a42db5f3062167bc77d2d2ae5b3e90da29c9e9d733a8b5316b1f57d8" } } ], "extra": [ 1, 74, 91, 248, 242, 122, 222, 247, 20, 85, 225, 205, 226, 58, 145, 202, 34, 246, 245, 104, 66, 136, 219, 98, 135, 139, 8, 194, 27, 85, 132, 211, 113, 2, 17, 0, 0, 0, 8, 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