Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eca8973b3f95a46a38ef926c4dc243e60d550ba774ad204c08b130d497a7aa3c

Tx prefix hash: 358c0cff8f96c7959c7dd3daa8485eb04378bc1d8242bddf4dfdfc4bce72ee6e
Tx public key: 47eb114e4c77cde9958a943ca8a9004ab7635bf29f348eda78f1193e68b5d746
Timestamp: 1665851914 Timestamp [UCT]: 2022-10-15 16:38:34 Age [y:d:h:m:s]: 02:186:12:31:25
Block: 609690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 654942 RingCT/type: yes/0
Extra: 0147eb114e4c77cde9958a943ca8a9004ab7635bf29f348eda78f1193e68b5d74602110000000133af99f4000000000000000000

1 output(s) for total of 5.859276343000 dcy

stealth address amount amount idx
00: a939f8fd53f17597280266ad377d6a1fb66749d4d5a5c7f5f14305e404d1d991 5.859276343000 1046550 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": 609700, "vin": [ { "gen": { "height": 609690 } } ], "vout": [ { "amount": 5859276343, "target": { "key": "a939f8fd53f17597280266ad377d6a1fb66749d4d5a5c7f5f14305e404d1d991" } } ], "extra": [ 1, 71, 235, 17, 78, 76, 119, 205, 233, 149, 138, 148, 60, 168, 169, 0, 74, 183, 99, 91, 242, 159, 52, 142, 218, 120, 241, 25, 62, 104, 181, 215, 70, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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