Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6b2b3c358c195a631bfd7b62e6441314c69c0268d531a7b85b8fa3a0599ad2f

Tx prefix hash: fc9ac8424df35f53cd7841594290ace165d2a0a4bd1eab00c4cd6cfce669f483
Tx public key: 3d19ef255b9132a6d2a69f6fd73782bd7ebb908b06d38b43aa151517301257a2
Timestamp: 1711804412 Timestamp [UCT]: 2024-03-30 13:13:32 Age [y:d:h:m:s]: 00:268:03:04:15
Block: 989634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191951 RingCT/type: yes/0
Extra: 013d19ef255b9132a6d2a69f6fd73782bd7ebb908b06d38b43aa151517301257a20211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56ae582e4ddd52279273ed5a57e4c93c1880446c81e8adb5819413c41b8f6b5d 0.600000000000 1449950 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": 989644, "vin": [ { "gen": { "height": 989634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56ae582e4ddd52279273ed5a57e4c93c1880446c81e8adb5819413c41b8f6b5d" } } ], "extra": [ 1, 61, 25, 239, 37, 91, 145, 50, 166, 210, 166, 159, 111, 215, 55, 130, 189, 126, 187, 144, 139, 6, 211, 139, 67, 170, 21, 21, 23, 48, 18, 87, 162, 2, 17, 0, 0, 0, 5, 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