Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b59f6ad92ad1b1f89367ae018d9dad62f01a527dc79df2bd86c797a77cf10486

Tx prefix hash: 09a6e53e62f449c789948a1e67668804f7e96a803c985d21103ca0862e31b7db
Tx public key: 5dc5791cd93c922b833f777e67db84f1221aa8d1605750a1c976c5817e80a69b
Timestamp: 1695521419 Timestamp [UCT]: 2023-09-24 02:10:19 Age [y:d:h:m:s]: 02:044:15:03:03
Block: 854808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551532 RingCT/type: yes/0
Extra: 015dc5791cd93c922b833f777e67db84f1221aa8d1605750a1c976c5817e80a69b021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.902955397000 dcy

stealth address amount amount idx
00: 092af7980bc568acb5e854b6d1e9112d99713d7255250233596053570da92c99 0.902955397000 1308798 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": 854818, "vin": [ { "gen": { "height": 854808 } } ], "vout": [ { "amount": 902955397, "target": { "key": "092af7980bc568acb5e854b6d1e9112d99713d7255250233596053570da92c99" } } ], "extra": [ 1, 93, 197, 121, 28, 217, 60, 146, 43, 131, 63, 119, 126, 103, 219, 132, 241, 34, 26, 168, 209, 96, 87, 80, 161, 201, 118, 197, 129, 126, 128, 166, 155, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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