Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f890664dd579659c3683734765a727b20d0f21df4be482bb663f3911af28db2e

Tx prefix hash: ae3e9f58446d2cff48c70fbcc9342b5238512c8bdd752f302d8cce3816b730b0
Tx public key: 03642816c6f3fbc81620b5b2322d73c796b50f40fa19e57048e03db86c83a4ed
Timestamp: 1656884108 Timestamp [UCT]: 2022-07-03 21:35:08 Age [y:d:h:m:s]: 02:178:22:20:15
Block: 536016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649210 RingCT/type: yes/0
Extra: 0103642816c6f3fbc81620b5b2322d73c796b50f40fa19e57048e03db86c83a4ed021100000010a8c141c5000000000000000000

1 output(s) for total of 10.279136517000 dcy

stealth address amount amount idx
00: b5d9664bf87bcde20c61feaa45aff4824966fa794e6df386be948395dcd65c3d 10.279136517000 965699 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": 536026, "vin": [ { "gen": { "height": 536016 } } ], "vout": [ { "amount": 10279136517, "target": { "key": "b5d9664bf87bcde20c61feaa45aff4824966fa794e6df386be948395dcd65c3d" } } ], "extra": [ 1, 3, 100, 40, 22, 198, 243, 251, 200, 22, 32, 181, 178, 50, 45, 115, 199, 150, 181, 15, 64, 250, 25, 229, 112, 72, 224, 61, 184, 108, 131, 164, 237, 2, 17, 0, 0, 0, 16, 168, 193, 65, 197, 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