Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23060f6830b494d6d7d1b51664d82bd737e248fef1dd2b294c7a2ecad33c6717

Tx prefix hash: 48643b2ca1af1d51f65ee33c954b81848fbf336b1489d5f87a07600df6b0b502
Tx public key: 5595dd8510f247294ec2b7dd669bc394d0cce8c70a32e1efd6a45dae9eed7855
Timestamp: 1686566512 Timestamp [UCT]: 2023-06-12 10:41:52 Age [y:d:h:m:s]: 01:200:19:18:27
Block: 780634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404890 RingCT/type: yes/0
Extra: 015595dd8510f247294ec2b7dd669bc394d0cce8c70a32e1efd6a45dae9eed78550211000000024b8f5122000000000000000000

1 output(s) for total of 1.590141088000 dcy

stealth address amount amount idx
00: c393f543a1dca6dc4d17fac432e178d6c254856070a9427ae04e2fba68a44d6d 1.590141088000 1230349 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": 780644, "vin": [ { "gen": { "height": 780634 } } ], "vout": [ { "amount": 1590141088, "target": { "key": "c393f543a1dca6dc4d17fac432e178d6c254856070a9427ae04e2fba68a44d6d" } } ], "extra": [ 1, 85, 149, 221, 133, 16, 242, 71, 41, 78, 194, 183, 221, 102, 155, 195, 148, 208, 204, 232, 199, 10, 50, 225, 239, 214, 164, 93, 174, 158, 237, 120, 85, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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