Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76aad43dc8e41e4cd49030db5faca79016c6961dadfd2d41b3f7a5b9c879d7ce

Tx prefix hash: 96e48efb3b889b1cac5068ec9f4a1590fc6a83afa1eb308084c7a708898117fb
Tx public key: 447bdae98596163656a831e353ca1cdc7a47c37ae82271adf2d6465439187ef9
Timestamp: 1581905929 Timestamp [UCT]: 2020-02-17 02:18:49 Age [y:d:h:m:s]: 05:063:01:43:37
Block: 66477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1198120 RingCT/type: yes/0
Extra: 01447bdae98596163656a831e353ca1cdc7a47c37ae82271adf2d6465439187ef902110000001b4943cd9f000000000000000000

1 output(s) for total of 369.608900033000 dcy

stealth address amount amount idx
00: fb1d825dbfe9695b808b43d974cc7b7ec8bcdc35d3a3325c4a2d1eff4980b4ef 369.608900033000 122438 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": 66487, "vin": [ { "gen": { "height": 66477 } } ], "vout": [ { "amount": 369608900033, "target": { "key": "fb1d825dbfe9695b808b43d974cc7b7ec8bcdc35d3a3325c4a2d1eff4980b4ef" } } ], "extra": [ 1, 68, 123, 218, 233, 133, 150, 22, 54, 86, 168, 49, 227, 83, 202, 28, 220, 122, 71, 195, 122, 232, 34, 113, 173, 242, 214, 70, 84, 57, 24, 126, 249, 2, 17, 0, 0, 0, 27, 73, 67, 205, 159, 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