Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8016f52449e53d480b5288278c6429b2436946f569cc6d7c44ca1bfb0ca89a26

Tx prefix hash: 4327f03a37adb8df208eb1351a04d7d6c10dada8048345035e3f2895c5d7c2d5
Tx public key: 11dca89625eaa88a2b1c29d6709435160417c14d5d96c7b339db9e6be9de0f5d
Timestamp: 1694820726 Timestamp [UCT]: 2023-09-15 23:32:06 Age [y:d:h:m:s]: 02:050:09:54:08
Block: 848998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555701 RingCT/type: yes/0
Extra: 0111dca89625eaa88a2b1c29d6709435160417c14d5d96c7b339db9e6be9de0f5d0211000000024b8f5122000000000000000000

1 output(s) for total of 0.943881009000 dcy

stealth address amount amount idx
00: 2f4decfbbdce2766a37dfa26046e071ebeff1492714138ca39e0abacbc68758a 0.943881009000 1302634 of 0

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": 849008, "vin": [ { "gen": { "height": 848998 } } ], "vout": [ { "amount": 943881009, "target": { "key": "2f4decfbbdce2766a37dfa26046e071ebeff1492714138ca39e0abacbc68758a" } } ], "extra": [ 1, 17, 220, 168, 150, 37, 234, 168, 138, 43, 28, 41, 214, 112, 148, 53, 22, 4, 23, 193, 77, 93, 150, 199, 179, 57, 219, 158, 107, 233, 222, 15, 93, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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