Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc7fecd0337d2102486a26db2a6bce770b713a008620e5a4174fa7281553775

Tx prefix hash: e5201d5a27c394c19e6ccdc6e36ba6b0e00824170c997df0014b8ed02393157d
Tx public key: 95d8cd1811d69f4699752fbc69e575d817ea2f8f69cc1cdfaae812e769ff95f1
Timestamp: 1733748648 Timestamp [UCT]: 2024-12-09 12:50:48 Age [y:d:h:m:s]: 00:115:08:18:39
Block: 1171440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82222 RingCT/type: yes/0
Extra: 0195d8cd1811d69f4699752fbc69e575d817ea2f8f69cc1cdfaae812e769ff95f1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a845ce8657161e4f67f5838b878665ec717d8921d81ac2e47c7a680f9d2a0a7f 0.600000000000 1657197 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": 1171450, "vin": [ { "gen": { "height": 1171440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a845ce8657161e4f67f5838b878665ec717d8921d81ac2e47c7a680f9d2a0a7f" } } ], "extra": [ 1, 149, 216, 205, 24, 17, 214, 159, 70, 153, 117, 47, 188, 105, 229, 117, 216, 23, 234, 47, 143, 105, 204, 28, 223, 170, 232, 18, 231, 105, 255, 149, 241, 2, 17, 0, 0, 0, 1, 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