Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65935bdbe38d9c84cdb59eeedfcc0393308c56390e43f7cb59000c739e673fd9

Tx prefix hash: 7dc89317ad7537f9f45e7967408ebe703124c69c1c20063951764078a8be9f16
Tx public key: 024436df6ca3e3bc8b0d4d2b1809902005f91b25d09676a57f1de7e8297d9ebd
Timestamp: 1733793785 Timestamp [UCT]: 2024-12-10 01:23:05 Age [y:d:h:m:s]: 00:189:17:10:38
Block: 1171817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135300 RingCT/type: yes/0
Extra: 01024436df6ca3e3bc8b0d4d2b1809902005f91b25d09676a57f1de7e8297d9ebd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a094dacca0e4bbf2ed7e61318d593d0b748b89dfab1c788e782ef99122099f4 0.600000000000 1657624 of 15

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": 1171827, "vin": [ { "gen": { "height": 1171817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a094dacca0e4bbf2ed7e61318d593d0b748b89dfab1c788e782ef99122099f4" } } ], "extra": [ 1, 2, 68, 54, 223, 108, 163, 227, 188, 139, 13, 77, 43, 24, 9, 144, 32, 5, 249, 27, 37, 208, 150, 118, 165, 127, 29, 231, 232, 41, 125, 158, 189, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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