Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f59151167bcb5f44cba01a1778ab1a541ccbad45c08f78a6c4968a4ba66ab0

Tx prefix hash: d80c8cd091735a5cb0466fcffce70b7c676c5d3dfaeab79816892de60b23ee82
Tx public key: 587f1c69f777774c7857e90c525b1f4253988ff3d4c8ad3995b821ee0fdb9b7f
Timestamp: 1740817103 Timestamp [UCT]: 2025-03-01 08:18:23 Age [y:d:h:m:s]: 00:101:21:09:54
Block: 1229677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72867 RingCT/type: yes/0
Extra: 01587f1c69f777774c7857e90c525b1f4253988ff3d4c8ad3995b821ee0fdb9b7f021100000001bc92c133000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cd8782fe885a3fce22820b695c5a946e2c7693d286802f05b91a2f4320f7d1b 0.600000000000 1716564 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": 1229687, "vin": [ { "gen": { "height": 1229677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cd8782fe885a3fce22820b695c5a946e2c7693d286802f05b91a2f4320f7d1b" } } ], "extra": [ 1, 88, 127, 28, 105, 247, 119, 119, 76, 120, 87, 233, 12, 82, 91, 31, 66, 83, 152, 143, 243, 212, 200, 173, 57, 149, 184, 33, 238, 15, 219, 155, 127, 2, 17, 0, 0, 0, 1, 188, 146, 193, 51, 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