Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 169d5dab355d40aa7be6d693bc9165a3266045bcc8130066f790a0e9c1ec4103

Tx prefix hash: 596fb20544a94e4bd5a6f4c2396cb6f0a97823aada9fa69dd3afa6bfa9751079
Tx public key: 552ec93e07e0007bb416971838d3b82d6f7b9ee06030881f988034c5f51f8c45
Timestamp: 1687007547 Timestamp [UCT]: 2023-06-17 13:12:27 Age [y:d:h:m:s]: 01:152:15:44:32
Block: 784288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370460 RingCT/type: yes/0
Extra: 01552ec93e07e0007bb416971838d3b82d6f7b9ee06030881f988034c5f51f8c45021100000001faf35c9c000000000000000000

1 output(s) for total of 1.546423481000 dcy

stealth address amount amount idx
00: b76183ca7135121b4ee33b83a2caa86d7959b242835127914ef89b8e1fa1cb6a 1.546423481000 1234175 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": 784298, "vin": [ { "gen": { "height": 784288 } } ], "vout": [ { "amount": 1546423481, "target": { "key": "b76183ca7135121b4ee33b83a2caa86d7959b242835127914ef89b8e1fa1cb6a" } } ], "extra": [ 1, 85, 46, 201, 62, 7, 224, 0, 123, 180, 22, 151, 24, 56, 211, 184, 45, 111, 123, 158, 224, 96, 48, 136, 31, 152, 128, 52, 197, 245, 31, 140, 69, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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