Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34fcd6133e21aa96475ab9f1619d39515d651ef072b11eddcc461b475bcd7a47

Tx prefix hash: 51cb83c5de0262e1e5a89b12bb260ea0be3676cdccca0f2401e5cdb4abcefead
Tx public key: bf96b82e82dc35e1c6081d4d278c162ca7d07c2ae0c60dba38aea9a19fc12850
Timestamp: 1707671386 Timestamp [UCT]: 2024-02-11 17:09:46 Age [y:d:h:m:s]: 00:315:13:21:43
Block: 955341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225948 RingCT/type: yes/0
Extra: 01bf96b82e82dc35e1c6081d4d278c162ca7d07c2ae0c60dba38aea9a19fc128500211000000070011055b000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 1369ef899fa37be27917fbbf4cc0072ce7ac79498813e64dc528c2fcdaf4b3d3 0.600010000000 1414627 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": 955351, "vin": [ { "gen": { "height": 955341 } } ], "vout": [ { "amount": 600010000, "target": { "key": "1369ef899fa37be27917fbbf4cc0072ce7ac79498813e64dc528c2fcdaf4b3d3" } } ], "extra": [ 1, 191, 150, 184, 46, 130, 220, 53, 225, 198, 8, 29, 77, 39, 140, 22, 44, 167, 208, 124, 42, 224, 198, 13, 186, 56, 174, 169, 161, 159, 193, 40, 80, 2, 17, 0, 0, 0, 7, 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